Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1791

reference: 794-tree-1
name: 1791
tree-preservation-order: undefined
794-tpo-1
uprn
address-text
point: POINT (-0.999507 50.866272)
geometry: MULTIPOLYGON (((-0.999422 50.866263,-0.999426 50.866280,-0.999438 50.866295,-0.999456 50.866307,-0.999480 50.866315,-0.999506 50.866318,-0.999533 50.866315,-0.999557 50.866308,-0.999576 50.866296,-0.999588 50.866281,-0.999593 50.866264,-0.999589 50.866248,-0.999577 50.866233,-0.999558 50.866221,-0.999535 50.866213,-0.999509 50.866210,-0.999482 50.866212,-0.999458 50.866220,-0.999439 50.866231,-0.999427 50.866246,-0.999422 50.866263)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL